This feature is specific to sites using RTGs or Forklifts.
When you generate a load plan, AutoStow tracks theoretical RTGs and forklifts throughout the yard as it plans each new move. To generate a load plan that is more realistic, XPS enables planners to specify RTG and forklift levels at the shift level.
Using this option, you can:
Specify the number of RTGs available for autostow (CFGRTL (on page 1)).
Specify the number of forklifts available for autostow (CFGFTL (on page 1)).
Specify whether each RTG or forklift is dedicated to the shift's POW or whether it is generally available for the vessel's work.
When you dedicate RTGs to a POW, the RTG calculator attempts to use only those RTGs for any job in the POW. However, the following exceptions apply:
When a different RTG covers the solution section, XPS uses that RTG.
When the solution block or lane has the maximum number of RTGs defined for that area (using the configuration parameters CFGRBL (on page 1) or CFGRLN (on page 1)), AutoStow uses one of the RTGs already present in that area. In this scenario, because there is a greater possibility of an RTG being blocked by another, AutoStow uses a non-dedicated RTG.
When none of the dedicated RTGs can get to the solution section without causing an RTG clash, AutoStow uses a non-dedicated RTG.
Specify whether AutoStow should assume that the shift's resources will be unavailable for loading when the POW is working a discharge work queue.
When you define the resources for each shift, AutoStow logs information about the RTGs that have been switched to Discharged or Parked state in the following windows:
AutoStow Notices window: Contains information on how AutoStow decides to deactivate RTGs. The best placed RTGs are left in place and all possible containers that could satisfy the next hour of projections are scanned.
RTG Schedule window: Contains information sorted by Scheduled Move Time. If you prefer to sort the same by RTG, set the XPS setting ASRTGT to N in the SPARCS Settings file.
When an RTG is in Discharged or Parked state, it is assumed to have moved from its last location and will not constrain the movement of actively loading RTGs.